[Vulkan] Implement initial support for sparse resources#684
Open
[Vulkan] Implement initial support for sparse resources#684
Conversation
s-perron
force-pushed
the
partially_mapped_resources_ots_i514
branch
4 times, most recently
from
8fdb37f to
3024d64
Compare
s-perron
force-pushed
the
partially_mapped_resources_ots_i514
branch
3 times, most recently
from
bb9c322 to
9d1d838
Compare
s-perron
force-pushed
the
partially_mapped_resources_ots_i514
branch
from
9d1d838 to
e1f0ad1
Compare
This commit introduces the ability to create and test sparse resources in the Vulkan backend. Key changes: - **Vulkan Backend**: Updated the Vulkan implementation to support sparse binding and residency for buffers. - **Test Infrastructure**: Enhanced test/lit.cfg.py to automatically detect and expose all boolean Vulkan features from api-query as lit features. This enables tests to use REQUIRE for specific hardware capabilities like sparseBinding and sparseResidencyBuffer. - **New Tests**: Added a suite of feature tests in test/Feature/Sparse/ to verify sparse resource behavior across different buffer types, including residency checks and partially mapped resource loads. This provides the necessary framework to validate sparse resource handling and residency behavior in HLSL-to-Vulkan pipelines.
s-perron
force-pushed
the
partially_mapped_resources_ots_i514
branch
from
e1f0ad1 to
ea571ac
Compare
Keenuts
reviewed
Apr 9, 2026
Keenuts
reviewed
Apr 10, 2026
Comment on lines
+1259
to
+1260
| // vkQueueBindSparse requires the queue to support SPARSI_BINDING. We assume | ||
| // the main queue supports it. |
Contributor
There was a problem hiding this comment.
This is irrelevant no? (We assume main queue supports it), since we take a queue with the sparse bit.
Comment on lines
+170
to
+171
| if isinstance(FeatureValue, bool) and FeatureValue: | ||
| config.available_features.add(FeatureName) |
Contributor
There was a problem hiding this comment.
This replaces line 159 through 166 no?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit introduces the ability to create and test sparse resources
in the Vulkan backend.
Key changes:
binding and residency for buffers.
detect and expose all boolean Vulkan features from api-query as lit
features. This enables tests to use REQUIRE for specific hardware
capabilities like sparseBinding and sparseResidencyBuffer.
to verify sparse resource behavior across different buffer types,
including residency checks and partially mapped resource loads.
This provides the necessary framework to validate sparse resource
handling and residency behavior in HLSL-to-Vulkan pipelines.